Enhanced service procedures using force measurement

ABSTRACT

An embodiment of the invention may include a method, computer program product and system for guided service procedure. The embodiment may include receiving feedback data from one or more of a plurality of sensors. Each of the plurality of sensors may detect a physical condition at a serviceable location within an item of equipment. The item of equipment may be undergoing a service procedure by an equipment servicer. The embodiment may include determining whether the received feedback data from one or more of the plurality of sensors exceeds a threshold value. Based on determining that the threshold value is exceeded, the embodiment may include alerting the equipment servicer during the service procedure.

BACKGROUND

The present invention relates to a system for servicing equipment, andmore specifically, to detecting physical conditions of components withinequipment.

The use of items of equipment is widespread across many industries andentities including commercial businesses, consumer businesses, and thegovernment. Implementing proper service procedures for an item ofequipment may help to promote the correct and intended operation of theserviced equipment. The knowledge of the technician performing theservice and their awareness of the physical condition of componentswithin an item of equipment may also influence the quality and outcomeof the service procedure.

BRIEF SUMMARY

An embodiment of the invention may include a method, computer programproduct and system for guided service procedure. The embodiment mayinclude receiving feedback data from one or more of a plurality ofsensors. Each of the plurality of sensors may detect a physicalcondition at a serviceable location within an item of equipment. Theitem of equipment may be undergoing a service procedure by an equipmentservicer. The embodiment may include determining whether the receivedfeedback data from one or more of the plurality of sensors exceeds athreshold value. Based on determining that the threshold value isexceeded, the embodiment may include alerting the equipment servicerduring the service procedure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a physical condition detectionsystem, in accordance with an embodiment of the present invention;

FIG. 2 is a flowchart illustrating the operations of the service consoleof FIG. 1, in accordance with an embodiment of the invention where thephysical condition detection system of FIG. 1 is active during a serviceprocedure;

FIG. 3 is a flowchart illustrating the operations of the service consoleof FIG. 1, in accordance with an embodiment of the invention where thephysical condition detection system of FIG. 1 is active during run-timeoperation;

FIG. 4 is a block diagram depicting the hardware components of thephysical condition detection system of FIG. 1, in accordance with anembodiment of the invention;

FIG. 5 depicts a cloud computing environment in accordance with anembodiment of the present invention; and

FIG. 6 depicts abstraction model layers in accordance with an embodimentof the present invention.

DETAILED DESCRIPTION

Service procedures for enterprise computing, medical, industrial,transportation, or other specialized equipment can be very complex.Servicing such complex items of equipment can be a challenge as it maypresent many opportunities for faults and mistakes to occur during theservice procedure which may cause equipment malfunctions and possiblydangerous situations. Malfunctions caused by, for example, accidentalcomponent damage, miss-seated connectors, or servicing an incorrectlocation are often not detected until a system utilizing the item ofequipment is attempted to be brought to normal power or operationalstatus. Malfunction detection at this point may result in undesirableoutcomes such as, equipment damage or extended outages of equipment use,lost productivity to clients, and increased service costs to maintainequipment.

Embodiments of the present invention disclose a physical conditiondetection system 100, described below, which provides a method forenhancing equipment service procedures by introducing corrective stepsbased on feedback from a system of internal sensors which can be used todetect physical conditions at serviceable locations. In embodiments ofthe invention, serviceable locations may include, for example, powersupplies, cable connectors, printed circuit board (“PCB”) connectors,computer hardware components, or other electrical and mechanicalcomponents within an item of equipment. In other embodiments,serviceable locations may include, for example, surfaces for whichdeflection can be measured and non-electrical connections such as achassis frame. The feedback from the system of sensors may be used tomonitor and correct a variety of situations. For example, if forces aredetected in unexpected connector locations, or forces are out ofacceptable tolerance limits for a given connector, service procedurescould be amended in real time to prompt the servicer to inspect fordamage or take appropriate corrective action. Furthermore, in anotherexample, unexpected forces detected while an item of equipment is innormal run-time operation could be recorded, used to trigger warnings,and aid in debugging the item of equipment at a later date.

Embodiments of the present invention will now be described in detailwith reference to the accompanying Figures.

FIG. 1 is a functional block diagram illustrating physical conditiondetection system 100, in accordance with an embodiment of the presentinvention. In an example embodiment, physical condition detection system100 may include equipment 101, console connector 110, and serviceconsole 112.

In an example embodiment, equipment 101 represents a platform to housephysical condition detection system 100. Equipment 101 may be any itemof specialized equipment used, for example, in a commercial, consumer,government, or public setting. Equipment 101 may include one or moreinput/output connectors 102, one or more card connectors 104, one ormore sensors 106A, one or more sensors 106B, and service monitor 108. Invarious other embodiments, equipment 101 may include a piece of complexmanufacturing/assembly line equipment or a piece of complex medicalequipment, such as an MRI machine. Additionally, in various otherembodiments, equipment 101 may include commercial, industrial, aviation,or marine equipment.

In embodiments of the invention, input/output connector 102 representsan electrical connector through which input and output devices may beconnected to equipment 101. In various embodiments, input/outputconnector 102 may be, for example, a power connectors, a pc cardadapter, an IBM GX adapter, an audio connector, a video connector, amodem, an Ethernet port, an infrared connector, a USB, a serialconnector, a parallel connector, fire wire, a WiFi connector, or anyother input/output connector known in the industry. In an exampleembodiment, three input/output connectors 102 are depicted, however,equipment 101 is not limited to three input/output connectors 102. In anexample embodiment, one input/output connector 102 may be a USB port,another input/output connector 102 may be an HDMI port, and yet anotherinput/output connector 102 may be an Ethernet port.

In embodiments of the invention, card connector 104 represents anelectrical connector into which a printed circuit board can be insertedto add functionality to equipment 101. In various embodiments, cardconnector 104 may be, for example, a peripheral component interconnect(“PCI”) slot, an accelerated graphics port (“AGP”), memory connectors,or any other electrical connector for PCBs known in the industry. Invarious other embodiments, card connector 104 may represent a bridgebetween critical components, rather than optional peripheral components.For example, in a cell phone with multiple printed circuit boardsconnected by ribbon connectors. In an example embodiment, three cardconnectors 104 are depicted, however, equipment 101 is not limited tothree card connectors 104. In an example embodiment, one card connector104 may be a slot for RAM, another card connector 104 may be a PCI slot,and yet another card connector 104 may be another PCI slot.

In embodiments of the invention, sensors 106A-B may monitor and detectphysical conditions at serviceable locations within equipment 101.Serviceable locations within equipment 101 may be, for example,mechanical connector locations, such as input/output connector 102 andcard connector 104. Serviceable locations within equipment 101 may alsoinclude non-electrical connections. In various embodiments, sensors106A-B may send back an analog signal representing a physical condition(e.g. pressure, force, voltage) and/or a discrete signal (e.g. properconnection, pressure switch) at serviceable locations within equipment101. Sensors 106A-B may also detect plugs/unplugs at serviceablelocations within equipment 101. Sensors 106A-B may be mechanical,electrical, optical, or based on any other sensor design known in theindustry for detecting physical conditions and providing feedback. Invarious embodiments, sensors 106A-B may include, for example, a straingauge mounted on a flat surface to measure deflection of that surface.Further examples may include a capacitive, acoustic, or optical sensorcould measure the distance between two points to check for deflection,and an optical sensor could check for alignment. In an exampleembodiment, one or more of sensors 106A-B may transmit feedback toservice monitor 108 upon detection of some predefined physical conditionor force at one or more serviceable locations within equipment 101. Inan example embodiment, sensor 106A may monitor physical conditions atone or more input/output connectors 102 and sensor 106B may monitorphysical conditions at one or more card connectors 104.

In embodiments of the invention, service monitor 108 may monitorfeedback from one or more sensors within equipment 101 and communicatesensor feedback to service console 112. In an example embodiment,service monitor 108 may be a microprocessor programmed to monitorfeedback from sensors 106A-B, located at various serviceable locationswithin equipment 101. Service monitor 108 may also be programmed totransmit, via some connection, feedback from sensors 106A-B to serviceconsole 112. Furthermore, service monitor 108, may be programmed toreceive data or commands from service console 112. In an exampleembodiment, service monitor 108 may monitor and receive feedback fromsensors 106A-B relating to the physical condition of serviceablelocations within equipment 101. Service monitor 108 may also transmit,over console connector 110, the received sensor feedback to serviceconsole 112.

In embodiments of the invention, console connector 110 represents ameans for connection and transmission of sensor feedback data fromsensors within equipment 101, to service console 112. In an embodiment,console connector 110 may be implemented with any architecture designedfor passing data and/or control information between processors (such asmicroprocessors) and peripheral devices. In another embodiment, consoleconnector 110 may be a coaxial cable, fiber optic cable, twisted paircable, Ethernet cable or any other type of cable for sending andreceiving information across a network. In an example embodiment,console connector 110 transmits sensor feedback data from servicemonitor 108 to service console 112.

In yet another embodiment, console connector 110 may be implementedthrough a network, such as the Internet, representing a worldwidecollection of networks and gateways to support communications betweendevices connected to the Internet. The network may include, for example,wired, wireless or fiber optic connections. In other embodiments,console connector 110 may be implemented as an intranet, a local areanetwork (LAN), or a wide area network (WAN). In general, consoleconnector 110 can be any combination of connections and protocols thatwill support communications between equipment 101 and service console112.

In embodiments of the invention, service console 112 represents a meansfor displaying information from one or more sensors, within equipment101, to an equipment servicer. Service console 112 may include serviceinterface 113 and service program 114. Service console 112 may beimplemented as a hardware management console, a desktop computer, anotebook or a laptop computer, a smart phone, a tablet computer, ahandheld device, a thin client, or any other electronic device orcomputing system known in the art, in accordance with embodiments of thepresent invention, and may each include internal and external hardwarecomponents, as depicted in further detail below with reference to FIG.4. Service console 112 may also be capable of hosting service interface113 and service program 114 and of sending and receiving data to andfrom equipment 101, through console connector 110. In an exampleembodiment, service console 112 may display data received from servicemonitor 108, via console connector 110. The received data may containinformation from sensors 106A-B located within equipment 101.Furthermore, in an example embodiment, service console 112 may alsodisplay suggested action in response to the received data.

In embodiments of the invention, service interface 113 includescomponents used to relay information to a user of service console 112,as well as receive input from a user and transmit the input to anapplication residing on service console 112. In an example embodiment,service interface 113 uses a combination of technologies and devices,such as device drivers, to provide a platform to enable users of serviceconsole 112 to interact with service program 114. In the exampleembodiment, service interface 113 receives input from a physical inputdevice, such as a touch screen or keyboard, via a device driver thatcorresponds to the physical input device. In an example embodiment,service interface 113 displays information from service program 114 to auser through a display.

In embodiments of the invention, service program 114 may interpretsensor data in accordance with embodiments of the physical conditiondetection system of FIG. 1. Service program 114 may be a softwareapplication or configuration in a software application capable ofinterpreting data received from one or more of sensors 106A-B located atserviceable locations within equipment 101. In an example embodiment,service program 114 may interpret sensor data received by serviceconsole 112, through console connector 110. The received data mayoriginate from one or more of sensors 106A-B and relate to detectedforces or physical conditions at one or more of input/output connectors102 and one or more card connectors 104, within equipment 101. Inanother embodiment, service program 114 may be located on equipment 101.The operations and functions of service program 114 are described infurther detail below with regard to FIGS. 2 and 3.

FIG. 2 shows a flowchart illustrating the operations of service program114 in accordance with an example embodiment of the invention where thephysical condition detection system of FIG. 1 is active during a serviceprocedure. Referring to step S210, an equipment servicer may begin aservice procedure on components, such as one or more input/outputconnector 102 and one or more card connectors 104, within equipment 101.In one embodiment, before an equipment servicer can begin a serviceprocedure on components within equipment 101, the equipment servicer mayfirst need to remove or open a service panel to expose the serviceablelocations. An electrical switch may be connected to a latch of theservice panel. Upon removal or opening of the service panel, anelectrical signal is sent to service program 114 to indicate that aservice procedure is active. In an example embodiment, an equipmentservicer may, upon initiation of a service procedure, set the servicestatus of equipment 101 as active by turning on a service statusindicator within service program 114.

Referring to step S220, service program 114 may receive sensor data fromequipment 101, while equipment 101 is undergoing a service procedure.The received data may include information from one or more of sensors106A-B, located at serviceable locations, such as input/output connector102 and card connector 104, within equipment 101. Service monitor 108,located within equipment 101, may monitor and collect the feedback datafrom sensors 106A-B for transmission to service program 114, via consoleconnector 110.

Referring to step S230, service program 114 may determine whether anerror exists at a serviceable location within equipment 101, based onthe received sensor data corresponding to the serviceable location. Inan example embodiment, an error may exist at a serviceable location ifthe sensor associated with that location detects an unexpected force ordetects a force which exceeds an accepted predetermined tolerance value,defined by service program 114. If an error exists at the serviceablelocation, service program 114 proceeds to step S250. If an error doesnot exist at the serviceable location, service program 114 proceeds tostep S230. In another embodiment, an error may exist at one or moreserviceable locations within equipment 101, if the feedback frommultiple sensors satisfies a multi-sensor consensus indicating anunexpected force, or if the combined feedback from multiple sensorsexceeds a predetermined threshold or tolerance value. For example, ifthree of four pressure sensors detected an unexpected force atserviceable locations within equipment 101.

Referring to step S240, service program 114 may determine whether or notthe service procedure is finished. The determination of whether theservice procedure is finished may be made via a servicer input, or usingadditional sensors in equipment 101. In one embodiment, the status ofthe service procedure may be determined by an electrical switchconnected to a latch of a service panel on equipment 101. Once a removedor opened service panel has been replaced or closed, the electricalsignal indicating an service procedure may be terminated. In an exampleembodiment, the status of the service procedure may be determined by aservice status indicator within service program 114. Upon completion ofa service procedure, the equipment servicer may then use service program114 to turn the service status indicator off. If the service statusindicator is on, service program 114 may determine that the serviceprocedure is not finished and return to step S210.

Referring to step S250, service program 114 may report the error to theequipment servicer. Service program 114 may also log the error madeduring the service procedure for future use in debugging orinvestigation into other problems that may arise in equipment 101.

Referring to step S260, service program 114 may amend the serviceprocedure in real time to ask the equipment servicer to confirm that aprevious step was completed correctly, inspect the serviceable locationfor damage, or to take some other corrective action. For example, ifservice program 114 reports to the equipment servicer that a forceexceeding some threshold value was detected at card connector 104,service program 114 may then ask the equipment servicer to inspect cardconnector 104 for damage. Once corrective action has been presented tothe equipment servicer, service program 114 proceeds to step S210.

FIG. 3 shows a flowchart illustrating the operations of service console112 in accordance with an example embodiment of the invention where thephysical condition detection system of FIG. 1 is active during run-timeoperation. Referring to step S310, service program 114 may receivesensor data from equipment 101, while equipment 101 is in run-timeoperation. The received data may include information from one or more ofsensors 106A-B, located at serviceable locations, such as input/outputconnector 102 and card connector 104, within equipment 101. Servicemonitor 108, located within equipment 101, may monitor and collect thefeedback data from sensors 106A-B for transmission to service program114, via console connector 110.

Referring to step S320, service program 114 determines whether an erroror fault exists at a serviceable location within equipment 101, based onthe received sensor data corresponding to the serviceable location. Inan example embodiment, an error or fault may exist at a serviceablelocation if the sensor associated with that location detects amechanical connector disconnect, an unexpected force, or a force whichexceeds an accepted predetermined tolerance value, defined by serviceprogram 114. If an error or fault exists at the serviceable location,service program 114 proceeds to step S330. If an error or fault does notexist at the serviceable location, service program 114 proceeds to stepS310. In another embodiment, an error may exist at one or moreserviceable locations within equipment 101, if the feedback frommultiple sensors satisfies a multi-sensor consensus indicating anunexpected force, or if the combined feedback from multiple sensorsexceeds a predetermined threshold or tolerance value. For example, ifthree of four sensors detected an unexpected force at serviceablelocations within equipment 101.

Referring to step S330, service program 114 determines the severity ofthe error or fault detected in step S320, based on predeterminedclassifications, stored within service program 114, of low severityerrors or faults and high severity errors or faults. For example, a highseverity error or fault may occur if a PCB adding functionality toequipment 101, via card connector 104, fails or becomes disconnected.Moreover, a low severity error may occur if an output device, such asdisplay, connected via input/output connector 102, fails or becomesdisconnected. If service program 114 determines that the severity of theerror or fault is high, service program 114 proceeds to step S340. Ifservice program 114 determines that the severity of the error or faultis low, service program 114 proceeds to step S350.

Referring to step S340, service program 114 may take emergency action inresponse to detection of a high severity error or fault. Continuousmonitoring of input/output connector 102 and card connector 104, withinequipment 101, allow action to be taken during run-time operation inresponse to potential safety issues. In an example embodiment, detectionof a high severity error or fault at a serviceable location withinequipment 101 may trigger emergency action in the form of displaying awarning to a user of service program 114, flashing a warning light, orplaying an audible alarm, while equipment 101 is in run-time operation.In an example embodiment, emergency action may also include the poweringoff of the serviceable location (e.g. input/output connector 102, cardconnector 104), within equipment 101, where the high severity error orfault was detected.

Referring to step S350, service program 114 may log the error or faultdetected in step S330 for analysis and for future use in debugging orinvestigation into other problems that may arise in equipment 101. In anembodiment, service program 114 may store the logged error or faultwithin a database located on service console 112 and request a serviceprocedure, performed by an equipment servicer, for the detected error inequipment 101.

In another embodiment, where the physical condition detection system ofFIG. 1 is active during run-time operation, service program 114 may,separately or additionally, utilize feedback from sensors 106A-B todetect potential tampering with components at serviceable locationswithin equipment 101. Service monitor 108 may continuously monitor thestates of one or more sensors 106A-B, within equipment 101, and transmitsensor data to service program 114, via console connector 110. If one ormore of sensors 106A-B detects a force outside of what is expectedduring run-time operation, service program 114 may log the event forinvestigation and notify the system administrator responsible foroperating equipment 101 of the potential need for maintenance, performedby an equipment servicer, within equipment 101.

In yet another embodiment, where the physical condition detection systemof FIG. 1 is active during run-time operation, service program 114 may,separately or additionally, utilize feedback from sensors 106A-B toimplement a plug odometer feature within equipment 101. Some specializeditems of equipment may be designed for a limited number of serviceoperations before sensitive connections or components wear out. In anembodiment, equipment 101 may be designed for a limited number ofservice operations. Service monitor 108 may continuously monitor theconnection states of one or more sensors 106A-B, within equipment 101,and transmit sensor data to service program 114, via console connector110. Each time one or more of sensors 106A-B detects a connection statein the form of a full or incomplete mechanical plug or other action atserviceable locations within equipment 101, service program 114 mayincrement a counter. Once the counter has reached a predeterminedthreshold value, service program 114 may log the event and notify anequipment servicer that a component within equipment 101 has reached theend of its service life and requires replacing.

FIG. 4 depicts a block diagram of components of service console 112, inaccordance with an illustrative embodiment of the present invention. Itshould be appreciated that FIG. 4 provides only an illustration of oneimplementation and does not imply any limitations with regard to theenvironments in which different embodiments may be implemented. Manymodifications to the depicted environment may be made.

Service console 112 includes communications fabric 902, which providescommunications between computer processor(s) 904, memory 906, persistentstorage 908, network adapter 912, and input/output (I/O) interface(s)914. Communications fabric 902 can be implemented with any architecturedesigned for passing data and/or control information between processors(such as microprocessors, communications and network processors, etc.),system memory, peripheral devices, and any other hardware componentswithin a system. For example, communications fabric 902 can beimplemented with one or more buses.

Memory 906 and persistent storage 908 are computer-readable storagemedia. In this embodiment, memory 906 includes random access memory(RAM) 916 and cache memory 918. In general, memory 906 can include anysuitable volatile or non-volatile computer-readable storage media.

The programs service interface 113 and service program 114 in serviceconsole 112 are stored in persistent storage 908 for execution by one ormore of the respective computer processors 904 via one or more memoriesof memory 906. In this embodiment, persistent storage 908 includes amagnetic hard disk drive. Alternatively, or in addition to a magnetichard disk drive, persistent storage 908 can include a solid state harddrive, a semiconductor storage device, read-only memory (ROM), erasableprogrammable read-only memory (EPROM), flash memory, or any othercomputer-readable storage media that is capable of storing programinstructions or digital information.

The media used by persistent storage 908 may also be removable. Forexample, a removable hard drive may be used for persistent storage 908.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer-readable storage medium that is also part of persistent storage908.

Network adapter 912, in these examples, provides for communications withother data processing systems or devices. In these examples, networkadapter 912 includes one or more network interface cards. Networkadapter 912 may provide communications through the use of either or bothphysical and wireless communications links. The programs serviceinterface 113 and service program 114 in service console 112 is may bedownloaded to persistent storage 908 through network adapter 912.

I/O interface(s) 914 allows for input and output of data with otherdevices that may be connected to service console 112. For example, I/Ointerface 914 may provide a connection to external devices 920 such as akeyboard, keypad, a touch screen, and/or some other suitable inputdevice. External devices 920 can also include portable computer-readablestorage media such as, for example, thumb drives, portable optical ormagnetic disks, and memory cards. Software and data used to practiceembodiments of the present invention, e.g., the programs serviceinterface 113 and service program 114 in service console 112, can bestored on such portable computer-readable storage media and can beloaded onto persistent storage 908 via I/O interface(s) 914. I/Ointerface(s) 914 can also connect to a display 922.

Display 922 provides a mechanism to display data to a user and may be,for example, a computer monitor.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

While steps of the disclosed method and components of the disclosedsystems and environments have been sequentially or serially identifiedusing numbers and letters, such numbering or lettering is not anindication that such steps must be performed in the order recited, andis merely provided to facilitate clear referencing of the method'ssteps. Furthermore, steps of the method may be performed in parallel toperform their described functionality.

It is to be understood that although this disclosure includes a detaileddescription on cloud computing, implementation of the teachings recitedherein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported, providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure that includes anetwork of interconnected nodes.

Referring now to FIG. 5, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 includes one or morecloud computing nodes 100 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 100 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 5 are intended to be illustrative only and that computing nodes100 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 6, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 5) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 10 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may include applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and physical condition detection system 96.Physical condition detection system 96 may relate to monitoring sensorfeedback from sensors located within an item of equipment and suggestingpossible action based on the sensor feedback.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Theterminology used herein was chosen to explain the principles of the oneor more embodiments, the practical application or technical improvementover technologies found in the marketplace, or to enable others ofordinary skill in the art to understand the embodiments. Variousmodifications, additions, substitutions, and the like will be apparentto those of ordinary skill in the art without departing from the scopeand spirit of the invention, as defined in the following claims.

1-7. (canceled)
 8. A computer program product for guided serviceprocedure, the computer program product comprising: one or morecomputer-readable storage devices and program instructions stored on atleast one of the one or more tangible storage devices, the programinstructions comprising: program instructions to receive feedback datafrom one or more of a plurality of sensors, wherein each of theplurality of sensors is detecting a physical condition at a serviceablelocation within an item of equipment, and wherein the item of equipmentis undergoing a service procedure by an equipment servicer; programinstructions to determine whether the received feedback data from one ormore of the plurality of sensors exceeds a threshold value; and based ondetermining that the threshold value is exceeded, program instructionsto alert the equipment servicer during the service procedure.
 9. Thecomputer program product of claim 8, wherein a serviceable locationwithin an item of equipment comprises a computer hardware component. 10.The computer program product of claim 8, wherein a physical condition ata serviceable location comprises an element from the group consistingof: a force, an alignment, a voltage, and a connection state.
 11. Thecomputer program product of claim 8, further comprising: programinstructions to determine whether the feedback data from the pluralityof sensors satisfies a consensus among the plurality of sensorsindicating an unexpected force; and based on determining that thefeedback data from the plurality of sensors satisfies a consensus amongthe plurality of sensors indicating an unexpected force, programinstructions to alert the equipment servicer during the serviceprocedure.
 12. The computer program product of claim 8, wherein alertingthe equipment servicer comprises an element from the group consistingof: program instructions to display corrective actions to the equipmentservicer, program instructions to display a warning to the equipmentservicer, program instructions to play an audible alarm, programinstructions to flash a warning light, and program instructions to poweroff a serviceable location.
 13. The computer program product of claim 8,further comprising: program instructions to receive feedback data fromone or more of a plurality of sensors, wherein each of the plurality ofsensors is detecting a physical condition at a serviceable locationwithin an item of equipment, and wherein the item of equipment is activeduring run-time operation outside of a service procedure; and based ondetermining that the received feedback from one or more of a pluralityof sensors exceeds the threshold value, program instructions to requestperformance of the service procedure by the equipment servicer.
 14. Thecomputer program product of claim 8, wherein undergoing a serviceprocedure comprises performing, by the equipment servicer, maintenanceon the item of equipment.
 15. A computer system for guided serviceprocedure, the computer system comprising: one or more processors, oneor more computer-readable memories, one or more computer-readabletangible storage devices, and program instructions stored on at leastone of the one or more storage devices for execution by at least of theone or more processors via at least one of the one or more memories, theprogram instructions comprising: program instructions to receivefeedback data from one or more of a plurality of sensors, wherein eachof the plurality of sensors is detecting a physical condition at aserviceable location within an item of equipment, and wherein the itemof equipment is undergoing a service procedure by an equipment servicer;program instructions to determine whether the received feedback datafrom one or more of the plurality of sensors exceeds a threshold value;and based on determining that the threshold value is exceeded, programinstructions to alert the equipment servicer during the serviceprocedure.
 16. The computer system of claim 15, wherein a serviceablelocation within an item of equipment comprises a computer hardwarecomponent.
 17. The computer system of claim 15, wherein a physicalcondition at a serviceable location comprises an element from the groupconsisting of: a force, an alignment, a voltage, and a connection state.18. The computer system of claim 15, further comprising: programinstructions to determine whether the feedback data from the pluralityof sensors satisfies a consensus among the plurality of sensorsindicating an unexpected force; and based on determining that thefeedback data from the plurality of sensors satisfies a consensus amongthe plurality of sensors indicating an unexpected force, programinstructions to alert the equipment servicer during the serviceprocedure.
 19. The computer system of claim 15, wherein alerting theequipment servicer comprises an element from the group consisting of:program instructions to display corrective actions to the equipmentservicer, program instructions to display a warning to the equipmentservicer, program instructions to play an audible alarm, programinstructions to flash a warning light, and program instructions to poweroff a serviceable location.
 20. The computer system of claim 15, furthercomprising: program instructions to receive feedback data from one ormore of a plurality of sensors, wherein each of the plurality of sensorsis detecting a physical condition at a serviceable location within anitem of equipment, and wherein the item of equipment is active duringrun-time operation outside of a service procedure; and based ondetermining that the received feedback from one or more of a pluralityof sensors exceeds the threshold value, program instructions to requestperformance of the service procedure by the equipment servicer.